Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: do not handle write errors after request is aborted #28722

Conversation

trop[bot]
Copy link
Contributor

@trop trop bot commented Apr 19, 2021

Backport of #28682

See that PR for details.

Notes: no-notes

This fixes a flake on linux CI which started recently where the "write"
promise is being rejected after the request has been aborted /
cancelled.  In this case we should drop the error to the floor but
instead we pass it down the stack where it eventually emits a now
unhandled error event.

Example failure: https://app.circleci.com/pipelines/github/electron/electron/38072/workflows/c1faf19b-aa41-4f99-a564-165729222859/jobs/838813

Verified fix by running the test that caused it 10000 times before fix
and 10000 times after.  ~50 failures before, 0 after.
@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Apr 19, 2021
@trop trop bot requested a review from MarshallOfSound April 19, 2021 13:51
@trop trop bot added 11-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes labels Apr 19, 2021
@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Apr 19, 2021
@MarshallOfSound MarshallOfSound merged commit 487c5c9 into 11-x-y Apr 19, 2021
@release-clerk
Copy link

release-clerk bot commented Apr 19, 2021

No Release Notes

@trop trop bot deleted the trop/11-x-y-bp-fix-do-not-handle-write-errors-after-request-is-aborted-1618840240721 branch April 19, 2021 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
11-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant